IBM 8270, 8271, AND 8272 LAN SWITCH ATM UFC RELEASE NOTES - VERSION 1.14.2 This set of release notes provides specific information for software release 1.14.2 for all of the ATM UFC for the IBM 8270, 8271, and 8272 LAN Switch, and for the 8271 and 8272 LAN Switch Module with an integrated ATM port. It documents important operating environment considerations. Herein, ATM UFC means both, the ATM Universal Feature Card and the integrated ATM port, unless otherwise stated. CONTENTS A. Latest Release Level of Software. B. Problems Fixed in the ATM UFC software. C. Known Problems/Anomalies/Design Points. D. Files on the Diskettes and Software Download Procedures. E. IBM 8270, 8271, and 8272 LAN Switch Specific Information. A. LATEST RELEASE LEVEL OF SOFTWARE This release of the ATM UFC software is a maintenance release which provides support for Emulated LANs (ELANs) on the 155 Mb/s ATM Universal Feature Card (UFC). The ATM UFC provides a LAN Emulation Proxy Client service, which in conjunction with the LAN Emulator Server functions within the ATM network, allows Token-Ring or Ethernet-attached stations to communicate with servers attached directly to ATM switches (e.g. 8260 ATM Campus Switch) or with stations or servers located on other 8270, 8271, or 8272 switches across the ATM Backbone. For ATM-specific information, please consult the ATM 155-Mbps Multimode Fiber Universal Feature Card - Planning and Installation Guide (GA27-4156-00). If the publications package that came with the product contains a set of release notes and diskette inside the shrink-wrapped package, they may be down-level and should be discarded. This set of release notes and diskette are the latest level as of the manufacturing date of your switch. Any updates to the release notes and switch software will be posted on the Internet and can be obtained using the World Wide Web URL: http://www.networking.ibm.com/support It is important to check the Web site to ensure that you are using the latest level of software. B. PROBLEMS FIXED IN THE ATM UFC SOFTWARE 1. Problems addressed in ATM UFC Release 1.14.2 a. Reliability 1) ATM UFC release 1.14.0 is not compatible with 8265 CPSW version F3.3.4 and prior 8265 CPSW versions. (8260 users are not affected by this problem.) A problem with the encoding of the system up-time by the ILMI code on the ATM UFC caused the 8265 to reset the ILMI layer at certain times after the 827x was powered on. The ILMI layer resets 10 minutes after the 827x completes diagnostics and again 46 hours later with CPSW version F3.3.4. With earlier CPSW versions the resets occurr at the 5 minute mark and at the 23 hour mark. The resets do not occur if ATM UFC Release 1.14.2 is used. 2) The serial download function in ATM UFC Release 1.13.0 through 1.14.1 does not work. If serial download of ATM UFC code is attempted, the operation will hang and a complete 827x switch reset is required to clear the condition. Also, if the ATM UFC main image becomes corrupted (e.g. if the 827x or the ATM UFC is reset during ATM UFC code download) an ATM UFC with these releases of boot(strap) code can not be restored using serial download and the UFC is rendered permanently inoper- able. It is NOT recommended to install any of the defective releases of boot(strap) code. ATM UFC Release 1.14.2 contains a fixed version of the boot(strap) code. If you need to install this level then see section D item 4 for boot code upgrade instructions. 2. Problems addressed in ATM UFC Release 1.14.0 a. Connectivity 1) The ATM UFC LEC(s) failed to rejoin the ELAN under certain recovery scenarios. These problems have been fixed. 2) The ATM Campus Manager could not discover and manage an 827x attached to an 8260 using ATM. This problem has been fixed. 3) Heavy LAN port traffic coinciding with overflowing LAN port address tables could cause data, control or multicast VCCs to drop. This has been fixed. 4) Under rare circumstances, an atm address may never be resolved for a destination MAC address. This problem has been fixed. 5) Particularly in networks with many ATM devices which periodically (but routinely) disconnect from the ATM network, the ATM UFC would occasionally lose information about certain VCCs (data, control, or multicast) causing the VCC to appear "UP" when in fact frames on that VCC were being discarded. This problem has been fixed. 6) Under certain conditions, a discrepancy existed between the ATM UFC and the 826x on what UNI version should be used. This problem has been fixed. 7) When an integrated ATM port was "isolated" from the 826x console, the port would fail to show "DOWN" on the 827x console. This problem has been fixed. b. Performance 1) The time required to detect a LES/BUS outage has been shortened to 4 seconds. Previously it could take up to 32 seconds using UNI 3.1 or 90 seconds using UNI 3.0 to detect certain LES/BUS outages. This new LES/BUS failure detection mechanism monitors traffic from the LES/BUS. When used in a network that includes a redundant LES/BUS this new mechanism will provide quicker switchover times from a primary LES/BUS to an alternate LES/BUS if the primary LES/BUS fails. See section C, "KNOWN PROBLEMS/ANOMALIES/DESIGN" item 10 "Data Direct VCC Keep Alive Timeout" for more information. 2) The domain mac address previously was registered as a LOCAL address. When a topology change occurred in the network, other LECs could take up to their configured C17 time (default is 5 minutes) to re-discover LOCALLY registered macs. The domain mac address is now registered as a REMOTE address to improve the re- discovery of the ATM UFC LEC by other LECs following a topology change. 3) Particularly in networks with many ATM devices which periodically (but routinely) disconnect from the ATM network, timers associ- ated with the le-arp table in the ATM UFC would become stuck, preventing proper table maintenance. This problem has been fixed. c. ATM UFC Resets 1) The ATM UFC may be reset as a result of an "Echo time-out" due to an ATM UFC specific internal error (FAULT PC=600, FAULT PC=200, or other reasons). These problems have been fixed. 3. Problems addressed in ATM UFC Release 1.12.3 a. Connectivity 1) The LE ARP cache size has been increased to 3400 entries. In the case of LE ARP cache overflow, the ATM UFC will now reuse entries in the LE ARP cache. 2) LE ARP cache entries management has been improved, preventing connection or session loss. 3) A problem with the first frame getting lost has been corrected. This problem prevented connection from being established or caused session loss. 4) An atm port reset or a LEC reset was sometimes required to get the LEC to rejoin the ELAN after a failure. The LEC now rejoins automatically. 5) When a LEC ID changed, the old LEC ID was still used by the data- direct VCC. This restricted communication with a device that has the old LEC ID. The ATM UFC code is now aware of the LEC ID changes. The user no longer has to set the Data Direct VCC Keep Alive Timeout to zero to bypass this problem. b. Performance 1) ATM UFC load (Boot) time is four times faster than previous releases. In order to make this active, the user must load this release of ATM UFC boot code. See section D item 4 for boot code upgrade instructions. 2) ATM UFC's re-assembly buffers recovery has been improved, pre- venting network "slowdowns" and ATM UFC hangs. 3) The frame processing power of the ATM UFC has been improved, pro- viding faster registration, address learning, and cell reception and transmission. 4. Problems addressed in ATM UFC Release 1.11.0 a. A data corruption problem has been fixed in this release. Users connected through IBM 8270/8272 LAN Switch ATM UFC experienced SNA session loss. A frame received from the ATM network was duplicated as it was passed to a Token-Ring port. This problem has been corrected. All users (8271/8270/8272) should upgrade the ATM UFC code to Release 1.11.0 b. The IBM 827x LAN Switch cold boot diagnostic could incorrectly detect a loopback test failure and disable the ATM UFC. This problem has been corrected. c. An ATM UFC port reset was sometimes required if a LAN Emulation Client failed to rejoin the Emulated LAN after a heavy traffic condi- tion with many learned addresses. This problem has been corrected. d. The AFC console has been enhanced in this release. e. A problem where end-station to end-station connectivity across the ATM network was lost has been corrected. Heavy traffic with many learned addresses could cause an out of buffer condition on the ATM UFC. Under this condition, the ATM UFC did not update the hardware filter tables that map MAC addresses to Virtual Circuit Identifiers to maintain end-station to end-station connectivity. f. An ATM UFC port reset was sometimes required when the ATM UFC reported "port is DOWN". The ATM UFC failed to restart the ILMI com- munication when the IBM 8260 155 blade was initially in ISOLATED mode, and then moved to CONNECTED/ENABLED or the IBM 8260 was reset. This problem has been corrected. g. A problem handling multiple incoming calls from the same LAN Emu- lation Client is fixed in this release. Normally, an ATM LAN emu- lation Client will make only one call at a time to the same destination and this code problem will not be apparent. However, certain misbehaving ATM LAN Emulation Client device drivers can issue many such calls and fill up the ATM UFC's data direct VCC table. An ATM port reset was required to recover from the problem. This problem has been corrected. h. IBM 8271 switch with ATM UFC experiencing up-link receive failures, requiring a reset of the ATM UFC has been corrected. 5. Problems addressed in ATM UFC Release 1.10.0 a. A problem where the ATM UFC used the wrong virtual circuit connection in the case of a call collision has been corrected. It is recom- mended to upgrade *ALL* ATM UFCs in your network to avoid interoper- ability problems with previous releases. In the case of a call collision, the call placed by the ATM Lan Emulation Client with the lower ATM address is to be used. In previous releases, each octet of the called ATM address was compared with the corresponding octet of the calling ATM address until a pair of octets was found that were not equal. If either of the octets of this pair contained a '1' in the most significant bit, the wrong switched virtual circuit would be used in the case of a call collision. The effects of this problem were observable when attempting to call an ATM LAN Emulation Client that did NOT contain this defect. b. A problem where end-station to end-station connectivity across the ATM network was lost has been corrected. If a data direct virtual circuit connection was taken down at a time when a duplicate data direct virtual circuit connection existed, the ATM UFC did not update the necessary hardware filter tables to maintain end-station to end- station connectivity. c. Users having intermittent connectivity problems through the ATM UFC has been corrected: 1) Under heavy traffic, the ATM UFC may not learn a burst of more than 200 addresses. 2) End-station to end-station connectivity across the ATM Network is lost. d. The switch resetting the ATM UFC due to "Echo Response" time-out has been resolved, specifically: 1) Heavy traffic through the ATM UFC. e. The time the ATM UFC takes to rejoin the ATM Emulated LAN has been shortened. For environments that include MSS redundancy, the switching time from primary MSS to backup MSS and vice-versa is improved. f. User having to reset the switch multiple times to get the ATM UFC registered has been corrected. g. The ATM UFC incorrectly responded to all LE_ARP REQUESTS for MAC address 00:00:00:00:00:00 has been fixed. 6. Problems addressed in ATM UFC Release 1.9.0 a. The ATM UFC network traffic slowing down and eventually stopping during heavy traffic has been corrected. 7. Problems addressed in ATM UFC Release 1.7.8 a. The resetting of the ATM feature card during heavy traffic or the learning of many unknown addresses has been corrected. b. Corrected ATM Statistics for 1) LEC Status/Statistics - MIB II Statistics 2) ATM Physical Port Status/Statistics c. Additional performance enhancements 1) Data throughput 2) Address learning d. Improved handling of the ILMI/Signalling packets e. Invalid LE ARP Response problem fixed. f. Data Direct and other connection issues resolved. g. Corrected the Legacy table update problem. h. LEC dropping problem has been resolved. 8. Problems addressed in ATM UFC Release 1.6.0 a. LAN Emulation Enhancements 1) The Data Direct VCC Keep Alive Timeout parameter can now be set by the user. 2) As long as the data direct keep alive timer is running, informa- tion to the spanning tree is deferred to prevent blocking of the port. After the data direct timer expires, if the LES/BUS is not re-acquired, the port state will be changed to LINK DOWN. b. External commands entered from the 8260 switch caused the port to hang in a state where the ATM prefix is learned but the LEC does not attempt to register it's ESI. Release 1.7.8 corrects this. c. SONET framer is now quiesced after a card reset to prevent extraneous CRC errors. d. ATM Card performance has been improved. e. A slow startup problem with SNA and Netbios sessions has been fixed. f. LEC MIB II Stats have been improved. Negative numbers were appearing before. g. If ATM card was installed in mod 216 slot 1-1 only, the ATM card would not work. This release corrects this problem. C. KNOWN PROBLEMS/ANOMALIES/DESIGN POINTS +--- IMPORTANT NOTICE ------------------------------------------------------+ | | | RULES for upgrading ATM UFC boot(strap) code. | | | | Please read ALL four rules. | | | | 1. Token-Ring switch users REQUIRE ATM UFC boot(strap) code Release | | 1.01.0 or later for proper operation of the ATM UFC. | | | | 2. For Ethernet Switch users, ATM UFC boot(strap) code Release 1.01.0 or | | later is recommended. | | | | 3. ATM_UFC boot(strap) code Releases 1.13.0 through 1.14.1 are defec- | | tive. These releases should not be installed. If a defective release | | of boot(strap) code has been installed, upgrading to a later release | | is recommended. | | | | 4. ATM UFC load (Boot) time is four times faster using boot(strap) | | Release 1.12.3, 1.14.2 (or later) than earlier releases. Upgrading | | boot(strap) code to take advantage of this performance improvement is | | optional. | | | | To determine the ATM UFC boot (strap) version installed in your ATM | | UFC(s), follow the following steps: | | | | 1. From the switch log-on screen, enter the password "diag" (no "") fol- | | lowed by the user-defined password. For example, if the user-defined | | password is "hello", then enter "diaghello". If there is no user- | | defined password then enter "diag". | | | | 2. Select the last option on the menu: AFC Debug Console. Then enter | | the ATM UFC port number when prompted. | | | | 3. Hit ENTER one or more times just to make sure you have connected to | | the ATM UFC debug console. | | | | 4. Enter the command VPD (case sensitive). This will display version | | information for both the operational (MAIN) image and the boot(strap) | | (BOOT) image. | | | | 5. Consult the RULES above to detemine if your boot(strap) code should | | be replaced. If you plan to replace the boot(strap) code go to | | section D item 4 for an explanation of the ATM UFC boot code down- | | load procedure. If you do not plan to replace the boot(strap) code | | then enter the command exit (or ctrl-b) to leave the AFC Debug | | Console. | | | +---------------------------------------------------------------------------+ 1. DO NOT PLUG OR UNPLUG THE ATM UFC WHILE THE 8270, 8271, OR 8272 IS POWERED ON. Inserting or removing the UFC with the LAN Switch powered on could result in permanent damage to the UFC. 2. The LAN segment number must be assigned, using the Source-Route Config- uration Panel, when the ATM UFC is used in a Token-Ring source-routed netwrok. The above action prevents IBM 8270/8272 LAN Switch learning the LAN segment number from explorer traffic on the network. The ATM LEC resets when the LAN segment number is learned from explorer traffic. The ATM LEC reset will disrupts any existing traffic. For information on how to assign the LAN segment number, see the IBM 8270/8272 LAN Switch Plan- ning and Installation Guide. 3. It is no longer necessary to set the Data Direct Vcc Keep Alive Timeout to zero. See section C, "KNOWN PROBLEMS/ANOMALIES/DESIGN", item 10, "Data Direct VCC Keep Alive Timeout" for important restrictions. 4. MAXIMUM VCCs -Table 1-1 on page 1-4 of the ATM Planning and Installation Guide indicates that the ATM 155 UFC can support 3072 VCCs distributed over all active LAN Emulation Clients This release of the ATM 155 UFC will support only 1000 data direct VCCs. The 1000 data direct VCCs are shared by the maximum 8 active LAN Emulation Clients. 5. MAXIMUM LE_ARP TABLE SIZE - The LE_ARP table size is limited to 3400 entries for this release of the ATM 155 UFC software. The 3400 entries are shared by all active LAN Emulation Clients. In the case of overflow, the ATM UFC will remove one of the last 340 entries to make room for the new one. 6. The two LED patterns shown in the Planning and Installation Guide for the ATM UFC, Chapter 6, Table 6-2, page 6-4, first row, show normal opera- tional status. Users experiencing network problems when either of these patterns is present should consult the Alternate Trouble Indicators listed in the fourth column of the table. 7. ATM Statistics Problems The following are known problems in ATM MIB II and console statistics for this release. These problems will be addressed in a future release. a. The statistics displayed on the following console panels may be incorrect and should not be considered accurate: o ATM Physical Port Statistics - MIB-II Statistics (from RFC 1573) o ATM Physical Port Status/Statistics o LEC Status/Statistics - MIB-II Statistics o LEC Status/Statistics - LAN Emulation Statistics b. ATM statistics can be accessed through the SNMP MIB objects. They may also be incorrect. 1) RFC1573 o ifTable - counters for ATM and LEC o ifXTable - counters for ATM and LEC 2) LECMIB o LEC Statistics Table - counters for ATM and LEC o LEC Status Table - units for C25 and C26 8. If user experiences connection delays, it is recommended that the Maximum Unknown Frame Count (C10) parameter be set to 10. 9. We now recommend that the Maximum unknown frame time (C11) and the Expected LE_ARP Response Time (C20) be the default value. 10. Data Direct VCC Keep Alive Timeout. This configurable parameter replaces the "Data Direct VCC after BUS failure" parameter found in early releases of the 827x ATM Feature. The data direct VCC keep alive timeout allows a user to configure how long the 827x ATM Feature will maintain its data direct VCCs to other LAN Emulation Clients, after it has detected unavailability of the LES/BUS. If a data direct connection existed prior to a disruption, and the ATM address of the station was learned prior to the LES/BUS connection dis- ruption, then traffic to and from the station continues to flow during the temporary disruption of the LES/BUS connection. The ATM Forum specifies that data direct VCCs should be taken down imme- diately upon detection of LES/BUS unavailability. Enter 0 seconds for 100% ATM Forum Compliant operation. If your network contains an alternate path to any of the destinations that are reachable through the ATM network, (for example, an Ethernet, Token-Ring, or alternate ATM path), you must set the data direct keep alive timeout small enough to avoid loops in your network. The data direct keep alive timeout plus the time that it takes the LEC to discover the absence of the LES/BUS must be smaller than the 802.1D spanning tree parameters Max Age plus Forward Delay for your network. DATA DIRECT KEEP ALIVE TIMEOUT PLUS LES/BUS FAILURE DETECTION TIME (4 SECONDS MAXIMUM) MUST BE SET LESS THAN OR EQUAL TO 802.1D MAX AGE PLUS 802.1D FORWARD DELAY. Spanning tree loops can be created if the above recommendation is not followed. The following diagram shows a network that has two paths between the ATM network and the token ring network. The 'backup' path is blocked by the 802.1D spanning tree protocol. ..................... . . . ATM ELAN . ..................... | | | XXX - port blocked by spanning tree | | ----------- ----------- | 827x - A | | 827x - B | ----------- ----------- | | ;...........; . token-ring . . - or - . . ethernet . ............. Assume that the ATM port of the 827x-B is blocked by the 802.1D spanning tree. It will remain in blocked state as long as BPDUs are received on that port. If the LES/BUS fails and no BPDUs are received for the MAX AGE time, the port will transition to the LISTENING state followed by the LEARNING state and then the FORWARDING state. The port will stay in LIS- TENING state for one forward delay time and in LEARNING state for one forwarding delay time. So, if the port fails to receive BPDUs for MAX AGE plus two times the FORWARD DELAY time, it will transition to the FOR- WARDING state. If the LES/BUS outage is short enough so that the Data Direct VCC Keep Alive Timeout timer is still running, the ATM UFC will not signal a LINK DOWN state to the spanning tree code. When the LES/BUS VCCs are re- established, the ports are re-attached to the ELAN as if there was no interruption. If the Data Direct VCC Keep Alive Timeout is set too long, both ports could be reattached to the ELAN in FORWARDING state causing a spanning tree loop. Frames can endlessly circulate in a loop causing extreme network congestion. Recommended settings for 802.1D spanning tree and Data Direct VCC Keep Alive Timeout: CASE 1 CASE 2 MAX AGE 20 sec 6 sec FORWARD DELAY 15 sec 4 sec Data Direct VCC Keep Alive Timeout 31 sec 6 sec The ATM UFC detects LES/BUS failures in a maximum of 4 seconds. A LES/BUS failure is detected if any of the control or multicast VCCs are released or if there were no packets received on any of the control or multicast VCCs for a period of 4 seconds. If the network is idle, 4 seconds of inactivity is normal. The ATM UFC will send an LE_ARP request for the all Fs mac address every second that the network is idle to dis- tinguish between an idle network and a LES/BUS failure. Configuration screen showing new parameter: -------------------------------------------------------------------- Advanced Configuration of a LEC - LAN Emulation Enhancements Slot 1 LEC Index 101 Port is UP Current Default LAN Emulation Enhancements Value Value Data Direct VCC Keep Alive Timeout 6 sec 34 sec Save and Return Cancel and Return Restore Defaults Cancel changes made to this panel and return to the previous panel. Use cursor keys to choose item. Press to confirm choice. Press to return to Main Menu. -------------------------------------------------------------------- D. FILES ON THE DISKETTES AND SOFTWARE DOWNLOAD PROCEDURES 1. The following files are contained on the diskette: ATM 155 MB/S UFC MICROCODE AND MIB DISKETTE - RELEASE 1.14.2 File name Contents ------------- ------------------------------------ a) ATM_1142.UFC ATM UFC code b) RFC1695.MIB ATM MIB c) RFC1695.DEF ATM MIB Compiler Object Definition d) LECMIB.MIB LAN Emulation Client MIB e) LECMIB.DEF LEC MIB Compiler Object Definition f) README.ATM 8270/8271/8272 Release Notes, Version 1.14.2 2. Item a) is the microcode for the ATM UFC feature. Items b), c), d), and e) are network management files that should be given to your network administrator. 3. To download the microcode: a. Select Download from the main menu. b. From the Download menu, select TFTP to be used for the download. c. Select UFC Image. o ATM_1142.UFC d. Initiate download. 4. How to download ATM UFC boot(strap) code. WARNING: THIS PROCEDURE MUST BE FOLLOWED EXACTLY TO AVOID RENDERING THE ATM UFC PERMANENTLY INOPER- ABLE, REQUIRING A NEW ATM UFC. READ AND UNDERSTAND THESE INSTRUCTIONS BEFORE ATTEMPTING TO DOWNLOAD THE ATM UFC BOOT(STRAP) CODE. IF YOU HAVE ANY QUESTIONS, OR PREFER TO BE GUIDED THROUGH THE ATM UFC BOOT(STRAP) UPDATE PROCEDURE, CALL IBM SUPPORT. TO MINIMIZE THE RISK OF FAILING TO RECOVER FROM AN INCOMPLETE ATM UFC BOOT DOWNLOAD, THE FOLLOWING ADDITIONAL ITEMS ARE RECOMMENDED: A. USE THE 827X SWITCH CONSOLE TO ACCESS THE DOWNLOAD MENUS (INSTEAD OF TELNET). B. CHOOSE A TIME TO UPGRADE THE BOOT CODE WHEN ATM UFC TRAFFIC IS LEAST HEAVY, OR MOVE THE FILE SERVER CONTAINING THE ATM UFC IMAGE TO A LAN PORT ON THE SWITCH YOU ARE MODIFYING (INSTEAD OF ON THE ATM PORT). C. A FAILED DOWNLOAD CAN TAKE UP TO 1 MINUTE TO TIMEOUT. PLEASE BE PATIENT FOR IT TO TERMINATE SO THAT BUILT-IN RECOVERY CODE HAS A CHANCE TO EXECUTE. D. RETRY FAILED BOOT DOWNLOAD AS SOON AS POSSIBLE, AND BEFORE THE 827X IS RESET AND BEFORE THE ATM UFC PORT IS RESET. Follow the steps below to update the ATM UFC boot(strap) code. Notice that these steps require that you download the new ATM UFC image as you normally do, reset the adapter, and follow special, additional steps to load new boot(strap) code to the ATM UFC. BOTH DOWNLOADS ARE REQUIRED TO ENSURE SAFE RECOVERY IN THE EVENT OF AN UNSUCCESSFUL DOWNLOAD. IF YOU HAVE ATM UFC OPERATIONAL (MAIN) CODE AT VERSION 1.02.0 OR LATER, THEN YOU CAN SAFELY SKIP TO STEP 2. [STEP 1] To prepare your system for safe ATM UFC boot(strap) download: a. Download the new ATM UFC main image ( ATM_1142.UFC) to the ATM UFC (see section D item 3). b. Reset the ATM UFC port (or optionally, reset the entire switch) so that the new image is operational. This includes the support for safer boot(strap) download. [STEP 2] To download the new ATM UFC boot(strap) from the image file: a. From the switch log-on screen, enter the password "diag" (no "") fol- lowed by the user-defined password For example, if the user-defined password is "hello", then enter "diaghello". If there is no user- defined password then enter "diag". b. Select the last option on the menu: AFC Debug Console. Then enter the ATM UFC port number when prompted. c. Hit ENTER one or more times just to make sure you have connected to the ATM UFC debug console. d. Enter the command "F2" (case sensitive, and no ""). This "enables" the boot(strap) code on the ATM UFC to be erased and reloaded with the next download to the adapter. You should see a message printed that confirms your request. If you do not see a message, try to enter the command again. Do not reset the switch or the ATM UFC before starting the download (see below). If you do, you will need to re-issue the "F2" command, as it is not saved following an ATM UFC restart. e. Enter the command VPD and RECORD the serial number and burned-in MAC address for future reference. f. Enter ctrl-B,and ctrl-N, to return to the switch console. If you are in TELNET, ctrl-B will take you out of TELNET, that is okay. TELNET back to the switch to return to the log-on screen. g. Download the ATM UFC code to the ATM UFC. WARNING: YOU CAN ONLY SELECT TFTP DOWNLOAD. A SERIAL PORT DOWNLOAD OF THE ATM UFC WILL RESTART THE ATM UFC, WHICH BY DEFAULT, RE-APPLIES WRITE PROTECTION TO THE BOOT CODE IN THE ATM UFC. Failure to complete the download of boot(strap) code IS FATAL to the adapter if you reset it before successfully completing the download. [STEP 3] To verify that the download of boot(strap) code to the ATM UFC was successful: a. From the switch log-on screen, enter the password "diag" (no "") fol- lowed by the user-defined password. For example, if the user-defined password is "hello", then enter "diaghello". If the user has not defined a password just enter "diag". b. Select the last option on the menu: AFC Debug Console. Then enter the ATM UFC port number when prompted. c. Hit ENTER one or more times just to make sure you have connected to the ATM UFC debug console. d. Enter the command VPD (again, case sensitive). This will display version information for both the operational (MAIN) image and the boot(strap) (BOOT) image. The BOOT image should be updated to the same version as the UFC download file (ie ATM_1142.UFC is version 1.14.2). Note the main image will not be updated to the same version until the ATM UFC is reset. If the boot image is not updated or is incorrect, DO NOT RESET THE UFC or SWITCH. DO NOT ATTEMPT A SERIAL DOWNLOAD to the ATM UFC. You can go back to step 2 and attempt to download the boot(trap) code again (TFTP only). If the version information for the BOOT image has not changed, it is likely that you did not enter the "F2" command in [STEP 2], or that you performed a SERIAL download instead of a TFTP download in [STEP 2]. If you are still unable to upgrade the ATM UFC Boot code, contact IBM Support before resetting the adapter or switch. E. IBM 8270, 8271, AND 8272 LAN SWITCH SPECIFIC INFORMATION +--- IMPORTANT NOTICE ------------------------------------------------------+ | | | Release 1.14.2 for the ATM UFC requires the following LAN Switch software | | releases (or later): | | | | 8270 4.0.2B | | | | 8271 4.0 | | | | 8272 4.0.2A | | | +---------------------------------------------------------------------------+ Please refer to the IBM 8270, 8271, and 8272 LAN Switch Release notes for more information or contact IBM support. END OF RELEASE NOTES.